We can default the port to 6379 and override it using a system property with the correct port. In our configuration we can use standard PropertyPlaceholderConfigurer

@rwinch I've added a commit that demonstrates the approach taken for integration testing of WAR based samples.

This fails for reasons we've discussed the other day - I've opened testcontainers/testcontainers-java#369.

I've updated the PR to pick up recent changes to Session API and module structure.

The previous problem is still present though. There is however some feedback on testcontainers/testcontainers-java#369.

Hi folks,

@testcontainers is here :)

I think I know why application server doesn't stop, I'll debug it on TestContainers' side.

Meanwhile could you please provide more details on why are you trying to run testcontainers' containers as WAR-ed app? :)

Hi @bsideup - thanks for taking a look at this!

Regarding the motivation, our build currently depends on Redis service being available, which is used for integration testing of both our Redis-backed components and sample applications that use those components. We'd like to standardize and improve our integration tests using TestContainers, which would also make Docker the only external service our build depends on.

Integration testing of Redis-backed components and sample apps that are Spring Boot based is straightforward using JUnit @ClassRule, however some sample apps are packaged as WARs and then integration tested on Tomcat using gretty plugins. Our idea with those sample apps was to introduce an application profile which would be used in those integration tests, and which would sort of embed Redis instance (via TestContainers) using approach demonstrated in testcontainers/testcontainers-java#369.

Thanks to @bsideup we have a workaround and are no longer blocked by testcontainers/testcontainers-java#369. I'll revisit the PR to address the integration testing of WAR based samples during this week.

This should be ready now with the latest updates to the PR.

Integration tests for RedisOperationsSessionRepository (as well as other Redis integration tests) are based on Redis 3.2.9.

Integration tests for JdbcOperationsSessionRepository on top of existing H2, HSQLDB and Derby based now also include:

• MariaDB 5.x & 10.x
• MySQL 5.x
• PostgreSQL 9.x

TestContainers also provide Oracle XE module, but this is problematic to include due to well know situation with availability of Oracle JDBC driver in public repos. There is also SQL Server module in the works, so we might include that once the release is out.

Regarding the tricky part of this PR, the integration testing of WAR based samples using Gretty, I've opted to introduce a separate Redis configuration which is activated with embedded-redis Spring profile. This way the original Redis/Session configuration classes were mostly untouched which is important since the guides include code snippets from those classes.

Let me know what you think @rwinch.

Can you please update the README and guides?

Can you please update the README and guides?

Done. I've added a reference to Docker as an alternative to Redis installation.

Thanks for the PR! This is now merged